Recipient location aware notifications in response to related posts

ABSTRACT

In one aspect, a method is provided, including the following method operations: receiving a request to generate a first post data item at a first location; providing for presentation of the first post data item at a second location; receiving a request to generate a second post data item at the second location, the second post data item being in reply to the first post data item; identifying a destination for notification about the second post data item; providing in association with the destination a notification identifying the second post data item, the notification being associated with the first location.

CLAIM OF PRIORITY

The present application claims priority to U.S. Provisional Patent Application No. 61/745,179, filed Dec. 21, 2012, entitled “Aggregating Interactions for Content Items,” the disclosure of which is incorporated by reference herein.

BACKGROUND

The present disclosure relates to methods, systems, and computer programs for integrating comments across multiple properties.

In recent years, the proliferation of the Internet has brought about significant changes in the ways users are able to interact with content and with each other. One example is the mechanism of commenting that is widely available on many internet properties. For a given internet page, users are able to create and leave comments which then become viewable to other users accessing the same internet page.

SUMMARY

Implementations of the present disclosure provide methods, systems, and computer programs for display of comments across multiple properties. It should be appreciated that the present disclosure can be implemented in numerous ways, e.g., a process, an apparatus, a system, a device or a method on a computer readable medium. Several implementations of the present disclosure are described below.

In accordance with some implementations, a method is provided, including: receiving a request to generate a first post data item at a first location; providing for presentation of the first post data item at a second location; receiving a request to generate a second post data item at the second location, the second post data item being in reply to the first post data item; identifying a destination for notification about the second post data item; providing in association with the destination a notification identifying the second post data item, the notification being associated with the first location; wherein the method is executed by one or more processors.

In some implementations, the first location is defined by a social network page; wherein the second location is defined by a content page; and wherein the social network page and the content page do not share a common domain.

In some implementations, the first location is defined by a content page; wherein the second location is defined by a social network page; and wherein the content page and the social network page do not share a common domain.

In some implementations, presenting the first post data item at the second location includes accessing a social graph of a first user from whom the request to generate the first post data item is received, and identifying a second user as a member of the social graph of the first user, the second user identified as accessing the second location.

In some implementations, the notification is defined by one or more of an e-mail, a private message, or an alert.

In some implementations, the first post data item is generated in reply to a third post data item, the third post data item being originally generated at the second location and presented at the first location.

In some implementations, the notification includes a link to the second post data item presented at the first location.

In some implementations, identifying the destination for notification associated with the first post data item includes accessing a notification tag associated with the first post data item.

In some implementations, the notification provides access to a moderation interface for approving or rejecting the second post data item for display at the first location.

In some implementations, when the second post data item is rejected, then the second post data item is not displayed at the first location except when a user accessing the first location is identified as the author of the second post data item.

In some implementations, the first location or the second location defines a service.

In some implementations, the second post data item is a direct reply to the first post data item.

In some implementations, the destination is the first location.

In some implementations, the notification is defined as sent from the first location.

In some implementations, the request to generate the first post data item is defined from a first application that is triggered to open by a second application.

In accordance with some implementations, a method is provided, including: identifying a user accessing a content item as a moderator or a non-moderator; identifying a comment, the comment being associated with the content item; determining a legitimacy score for the comment; providing the comment for display in association with the content item when the legitimacy score for the comment falls within a first range; providing the comment for display in association with the content item when the user is identified as a moderator when the legitimacy score for the comment falls within a second range; excluding the comment when the legitimacy score for the comment falls within a third range; wherein the method is executed by one or more processors.

In some implementations, providing the comment for display in association with the content item when the user is identified as a moderator includes providing an interface to approve or reject the comment for display.

In some implementations, when the comment is rejected for display, then providing the comment for display in association with the content item when the user is identified as an author of the comment.

In some implementations, identifying the user further includes determining whether the user is a banned user, wherein when the user is identified as a banned user, then preventing the display of the comment in association with the content item.

In some implementations, preventing the display of the comment occurs except when the user is identified as an author of the comment.

In some implementations, the method further includes: determining whether content of the comment matches a predefined content, wherein when the content of the comment matches the predefined content, then providing the comment for display in association with the content item when the user is identified as a moderator.

In some implementations, the content item is received from a first location, and the comment is evaluated for display in association with the content item at a second location.

These and other implementations may provide one or more of the following advantages. Various implementations provide for display of post data items (e.g. comments, postings, etc.) across various properties. Comments/posts which are about a single subject or content item, but which were generated on different properties, can be made available for display on any property presenting the same subject or content item. In this manner, conversations which would otherwise only appear in disparate locations, can be unified for presentation in the same location when appropriate. Additionally, display of comments can be based on social graph data to provide an experience that is tailored to the viewer. For example, the viewer may see comments which are generated by users in his/her social graph prioritized for viewing, thereby providing a personalized experience.

Other aspects will become apparent from the following detailed description, taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure may be understood by reference to the following description taken in conjunction with the accompanying drawings.

FIG. 1 illustrates an example architecture of a system for implementing implementations of the disclosure, in accordance with implementations of the present disclosure.

FIG. 2 illustrates post data items posted on a social network page being made available for display on a content page, in accordance with implementations of the disclosure.

FIG. 3 illustrates posting of a comment on a website, in accordance with implementations of the disclosure.

FIG. 4 illustrates a method for displaying comments or postings across various properties, in accordance with implementations of the disclosure.

FIG. 5A illustrates a system for comment display, in accordance with implementations of the present disclosure.

FIG. 5B illustrates a system for display of comments or postings, in accordance with implementations of the disclosure.

FIG. 5C illustrates the generation of a comment in response to particular content viewed on mobile device, in accordance with implementations of the disclosure.

FIG. 5D illustrates a system for generating comments related to a content item, in accordance with the implementations described with reference to FIG. 5C.

FIG. 6 conceptually illustrates a post about a content item, and a subsequent post about the earlier post, in accordance with implementations of the disclosure.

FIG. 7A illustrates an interface for moderating comments about a content item by an owner of the content item, in accordance with implementations of the disclosure.

FIG. 7B illustrates an interface for moderating comments which have been posted relating to a content item, in accordance with implementations of the disclosure.

FIG. 8A illustrates a method for handling the display of comments on a page, in accordance with implementations of the disclosure.

FIG. 8B illustrates a method for displaying posts on an owner's page based on predefined moderation settings, in accordance with implementations of the disclosure.

FIG. 9 illustrates a system for filtering the display of comments on a property webpage, based in part on social network data, in accordance with implementations of the disclosure.

FIG. 10 conceptually illustrates the display of a private post based on the user viewing a content page, in accordance with implementations of the disclosure.

FIG. 11 conceptually illustrates the posting of a public post to a social network, in accordance with implementations of the disclosure.

FIG. 12 illustrates a method for notifying an author of a new post relating to their content item, and for displaying the new post as part of the content item's posting stream, in accordance with implementations of the disclosure.

FIG. 13 illustrates a system for notifying an author of a newly generated post which references or includes content of the author, in accordance with implementations of the disclosure.

FIG. 14 illustrates a flow of comments amongst a news cluster, in accordance with implementations of the disclosure.

FIG. 15 illustrates various identifiers defined for objects relating to posts, in accordance with implementations of the disclosure.

FIGS. 16A and 16B illustrate an example scenario involving posts by different users at different locations and the resultant notifications the different users are shown, in accordance with implementations of the disclosure.

FIG. 17A, illustrates a method for handling and moderating a new comment, in accordance with implementations of the disclosure.

FIG. 17B illustrates a method for determining whether to display or hide a comment from a user view, in accordance with implementations of the disclosure.

FIG. 18 is a schematic diagram of a computer system for implementing implementations of the present disclosure.

DETAILED DESCRIPTION

The following implementations describe methods, computer programs, and systems for the display of comments across multiple properties.

It will be apparent, that the present implementations may be practiced without some or all of these specific details.

FIG. 1 provides one example architecture of a system that may utilize implementations described herein. Users 124 interact with each other in the context of a social network, where users can include real people and entities. Each user has an account in the social network, and the account includes at least a user name. In addition, each account can include a profile of the user with additional information about the user, e.g., birth date, residence, favorite activities, etc. The user can be in control of what information is added to the profile, and what information is shared with others. A user may access the social network through different devices, e.g., a smart phone 114, a tablet computer 116, a laptop 118, a mobile phone 120, a personal computer 122, or any computing device that provides access to the Internet. Of course, the illustrated devices are only examples.

In accordance with some implementations, social network server 106 delivers services that enable users to interface with each other. The social network provides a site that enables users to define user accounts, which can be accounts for people and entity accounts. Through those accounts, users are able to connect with their friends, group of friends, entities, groups of entities, etc. In some implementations, the relationships established in the social network may be utilized in other contexts. Processing server 102 can be configured to perform various additional functions related to the social network, e.g., executing applications which run within the social networking environment, or processing data relating to external sites which have integrated social functionality. Search server 104 provides Internet search capabilities.

It is noted that the implementations illustrated in FIG. 1 are illustrative of certain implementations. Other implementations may utilize different servers, have the functionality of one server distributed over a plurality of servers, have the functionality of two or more servers combined into a single server, have a different amount of user categories in the social network, categorize users by different criteria, etc. The implementations illustrated in FIG. 1 should therefore not be interpreted to be exclusive or limiting, but rather illustrative.

FIG. 2 illustrates post data items posted on a social network page being made available for display on a content page. For purposes of the present disclosure, a post, posting, or comment can be understood as post data items, and the terms may be used interchangeably to identify user-generated content that is posted on a web page or property. For example, in the context of a social network, users typically generate “posts” or “postings” that appear in their news feed and that of their friends, whereas on a content website, users typically generate “comments” in response to certain content featured on the website. However, each of these pieces of user-generated data (post, posting, comment, etc.) may be characterized as post data items that can by made available for display across properties. These post data items are typically displayed in “feeds” or “streams” on social networking pages or content webpages containing content to which the post data items pertain. In the illustrated implementation, the social network page 200 of a user A is shown. A profile picture 202 is included in the social network page 200. A home button 204 directs to a home view of the user A's social network account. A profile button 206 directs to profile information and settings. A photos button 208 provides access to the user A's photos stored on the social network. The groups button 210 provides access to organizational groups into which users who are connected to user A on the social network may be organized. Other buttons or links may be provided to various other aspects of user A's social network account, in accordance with various implementations of the present disclosure.

To create a new posting on the social network, the user A may enter text into a text box 212. An attachment button 214 enables the user to insert a content item into the post, e.g. a picture, audio, or video. Insertion of the content item may entail submission of a URL of the content item. In some implementations, when a URL is entered into the text box 212, the URL is identified and a presentation of the content located by the URL is shown in the posting. When the user A has completed writing the text and inserting any content items into the post, the user can create and share the post on the social network by pressing the share button 216.

In the illustrated view of the user A's social network page, a news feed 217 is provided, which displays various postings by friends of the user and those of the user A. The user A has created a posting 222, which has an associated identifier 220, including a profile picture and name, that user A is the author of the posting 222. The posting 222 includes a link 223 to a content item 234 available on a separate website “anywebsite.com.” In response to user A's posting 222, users B and C have posted responses 224 and 226, respectively. The posting 222 and its associated responses 224 and 266 collectively define a posting unit 218. User A's news feed 217 also includes a posting 228 by a user D which includes a picture 230.

The page 232 of the website “anywebsite.com” provides access to the content item 234, for which user A's post 222 included a link. It will be appreciated that in various implementations, the link 223 can be a link to the content item 234 itself, or a link to the page 232 which presents the content item 234, or a link to some other page or resource which provides access to the content item 234. It will also be appreciated that the content item 234 can be any of various kinds of content, including image content, audio content, video content, textual content, etc. The page 232 includes a comments section 236, in which users may post comments and view comments posted by others. For example, in the text box 238, a user may enter text to create a new comment that is ostensibly about the content item 234 shown on the page 232. In the illustrated implementation, a comment 240 has been posted by a user E.

As the posting 222 includes a link to the content item 234, the posting unit 218 is about or otherwise relevant to the content item 234. It may therefore be desirable to include the posting unit 218 within the comments section 236 of the page 232 presenting the content item 234. In the illustrated implementation, the posting 222 as well as the responses 224 and 226 which together define the posting unit 218 are identified as relating to the content item 234 or page 232 and are therefore included in the comments section 236 of the page 232. When the posting 222 is displayed on the page 232 of the content website, the link 223 may be removed, as it is redundant in view of the page 232 featuring the content 234. The posting unit 218 originated on the social network, but is made available for display on the website hosting the content referenced by the posting 222. In this manner, user-generated content on one site (or property or location) that relates to content of another site can be synchronized and displayed across both sites.

FIG. 3 illustrates posting of a comment on a website. In the illustrated implementation, the user A is logged in to the website and accesses the page 300 of the website. The page 300 features content 302, which may be any of various kinds of content in accordance with various implementations of the disclosure. The user A may click in the box 304 to enter text for a new comment to be posted in the comments section 310 of the page 300.

The comments shown in the comments section 310 may be selectively displayed or sorted based on various characteristics of the comments. For example, a drop-down menu 306 is provided to enable the user to select from various sort criteria, such as sorting by the most recent or highest rated comments. (Comments may include a mechanism enabling users to express approval or disapproval of a comment, thereby conferring a rating for a comment based on the approval or disapproval expressed by users.) In the illustrated implementation, a “Top comments” sorting may establish a sort of the comments based on a variety of criteria, such as a combination of recency and rating, in addition to other factors. Additional factors can include, by way of example, whether or not the author of a comment is in the social graph of the current user, the number of responses to a comment, the length of a comment and/or its responses, the inclusion of links in a comment, the inclusion of predefined keywords in a comment, geographic proximity of the author of a comment to the viewer, language of a comment, etc.

A checkbox 308 enables the user A to configure the comments section 310 to display only comments from users that are in the user A's social graph.

When the user A clicks on the box 304 to define a new comment, he/she can be presented with additional options relating to the new comment. For example, in a box 312, the user A can designate those to whom the comment will be shared. In the illustrated implementation, by default a public designation 314 indicates that the comment will be shared with the public, meaning that the comment will be visible to any other user visiting the page 300.

A checkbox 316 allows the user A to share the new comment to his/her social graph on a social network. By clicking on an edit link 318, the user A can choose from various groups of users within user A's social graph to whom the comment will be shared on the social network. The new comment will therefore appear as a posting within the social network news feed of those users within the designated groups of user A's social network. In some implementations, the comment may have a link to the page 300, or some other identifier of the page 300 or content 302, appended to it when displayed in news feeds of users on the social network. In this manner, context for the comment is provided when it is displayed on the social network.

FIG. 4 illustrates a method for displaying comments or postings across various locations, e.g., on one or more properties, websites, or other locational instances. At method operation 400, a comment is created. At method operation 402, the comment is analyzed to identify content that is referenced by the comment. In some implementations, the identification of the content can entail identification of a URL or other identifier of content referenced by the comment. At method operation 404, an identifier, e.g., a canonical identifier (ID), is determined for the identified content. The canonical ID may be, in the case of an included URL serving as the identifier of content referenced by the comment, the URL itself or a canonical URL that is determined based on the URL included in the comment.

A canonical ID is a singular identifier associated with a content item or a content reference. Multiple content items or their references can be associated with the same canonical ID. However, no two canonical ID's can be assigned to the same content item or content reference. By way of example, multiple URL's may locate substantially the same content item (e.g. different URL's may direct/redirect to the same web page or item, or to different instances of an item that are substantially the same), separate media files may differ in structure (e.g. different compression, bitrate, encoding scheme, etc.) while encoding for the same underlying content, etc. A process for association of a canonical ID with a specific content item or its reference can include analysis of the content item to determine if it is similar to another content item by greater than a predefined threshold. If so, then the two content items determined to be substantially similar and are associated with the same canonical ID. A content item that is determined to not be substantially similar to another content item can be associated with its own unique canonical ID that is not shared with other content items.

At method operation 406, the comment is tagged with the determined canonical ID. At method operation 408, in response to a request for comments related to the content, a search is performed for comments that have been tagged with the canonical ID. The request for comments related to the content can be made in service of or as part of a request for a page featuring the content identified by the canonical ID. It will be appreciated that in accordance with the presently described method, comments can be created on any property (e.g. original host site of the content, social network, third-party websites, mobile application, etc.) that affords users the ability to create a comment referencing the content, and because such comments will be tagged with the same canonical ID, a subsequent search for comments based on the canonical ID will return all of these comments regardless of their origin. In this manner, comments which can be identified as relating to a specific content can be displayed across multiple properties.

FIG. 5A illustrates a system for comment display, in accordance with implementations of the present disclosure. A comment generator 500 includes a GUI for creation of a comment. According to the GUI, input is received to define the comment. A comment analyzer 504 analyzes the comment to identify content referenced by the comment, such as by the inclusion of a URL in the comment. A tagging module 506 references a canonical ID storage 508 to determine a canonical ID for the identified content referenced by the comment, and tags the comment with the canonical ID. The comment is stored in a comment storage 510.

A user 524 operates a device 522 to request a page, featuring the content, from web server 514. The web server 514 includes a content retrieval module 516 for retrieving content for the requested page from a content data storage 512. A comment retrieval module 518 retrieves comments from the comment storage 510 related to the retrieved content for the requested page. The related comments are retrieved by searching for comments tagged with a canonical ID associated with the retrieved content for the requested page. A page assembly module 520 assembles the requested page before serving it to the device 522 for consumption by the user 524.

FIG. 5B illustrates a system for display of comments or postings, in accordance with implementations of the disclosure. The web server 520 includes page assembly module 520, which retrieves a comments widget for inclusion in a page that is sent to device 522 for rendering. The comments widget 532 can be presented in an iframe as part of page 528, alongside content 530 of the page 528. The comments widget 532 is configured to retrieve comments from the comment storage 510 which are relevant to the content 530 shown on the page 528.

FIG. 5C illustrates the generation of a comment in response to particular content viewed on mobile device, in accordance with implementations of the disclosure. In the illustrated implementation, a mobile device 540 includes a display 542. A user accessing an application A may be presented with a view 544 of a particular content item. In the illustrated implementation, an article is shown in the view 544, though it will be appreciated that any kind of content item can be displayed. A button 548 is provided to allow the user to view comments or add a new comment in response to viewing the article. The button 548, when triggered, is configured to open a second application B that is configured to handle comments for the content item.

When the application B is executed, it provides a view 550. In the view 550, a representation or other identification of the content item for which comments are presented in the view 550 is provided. By way of example, the title 552 of the article is displayed, and may be defined to include an embedded link to the article. Various comments 556 which relate to the article are shown in the view 550. As discussed elsewhere herein, the comments 556 may include comments which have been originally generated at different locations or properties, but which can be aggregated and retrieved in accordance with systems and methods of the present disclosure. Additionally, a comment entry field 554 is provided to allow the user to enter text to define a new comment that will be associated with the article.

In some implementations, the user may additionally interact with the comments 556 which a been posted by other users. For example, a given comment 558 may be selectable to access additional features related to the comment 558, such as allowing the user to reply to the comment 558, or share the comment 558 to a social graph of the user on a social network.

Additionally shown in the view 544 provided by the application A is a button 546 configured to allow the user to share the article to their social graph on a social network. With continued reference to FIG. 5C, when the button 546 is activated, a view 560 is provided to facilitate generation of a new post sharing the article to the social network. It will be appreciated that the view 560 may be provided by the same application A or by separate application distinct from application A, such as a dedicated application for interacting with the social network. In the illustrated implementation, a sharing interface provided in the view 560 includes a reference 564 to the article (e.g. the title or a preview of the article), as well as a text entry field 562 wherein the user may enter text to be included as part of the posting to the social network. The user may designate specific members of the user's social graph to receive the new post in a recipients field 566.

A share button 568 triggers the generation of a new post as defined above which shares the article to the social network. A cancellation button 570 can be pressed to cancel the generation of the new post. It will be appreciated that a newly generated post to the social network as has been described may appear in other contexts wherein comments or posts related to the article are aggregated, such as the view 550 provided by the application B.

Each of the application A and the application B may be any of various types of applications configured to execute on the mobile device 540, provided that each is capable of providing the functionality less described. In some implementations the application A is a web browser or an application incorporating native web browser functionality. In other implementations, the application A is a dedicated application configured to retrieve and present the content apart from the native web browser functionality. The application B is a distinct application from the application A. In some implementations, the application B is a social networking application. In some implementations, the view 560 for sharing the article to the social network is provided by the same application B. Thus, the view 550 and the view 560 may be provided by different interfaces from the same social networking application executing on the mobile device 540.

FIG. 5D illustrates a system for generating comments related to a content item, in accordance with the implementations described with reference to FIG. 5C. Mobile device 540 includes at least one processor 571, memory 572, display 542, and an operating system 573. The application A indicated by reference 574 is defined to include a content retrieval module 575. The content retrieval module 575 is configured to request and retrieve content from a content server 586 over a network 585. In response to a given request, the content server 586 may in turn retrieve and serve a given content item from a content data storage 587.

The application A further includes a content presenter 576 that is configured to present a content item 577 on the mobile device 540, such as by rendering the content item on the display 542. A comments module 578 is configured to activate/open (initiate execution if not open, or bring to foreground if already executing in the background) the application B (shown at reference 580) on the mobile device 540. The comments module 578 provides the functionality described with reference to button 548 shown at FIG. 5C. In some implementations, the comments module 578 is defined as a permanent portion of the application A. In other implementations, the comments module 578 is downloaded in conjunction with other content for presentation by the application A.

Comments module 578 can be defined by a code portion which defines both a triggering mechanism and an API call to open the application B in accordance with the operating system 573 of the mobile device 540. The API call may define an operating system-specific URL locating the application B. Furthermore, the API call includes a content parameter which identifies the content item for which comments are to be displayed or generated by the application B. This content parameter is passed to the application B, and is utilized by the application B to identify the content item view by the user in the previous application A, and thereby provide the appropriate representation of the content item as well as the relevant comments for that content item. In some implementations, the content parameter is a canonical identifier for the content item. In other implementations, the content parameter is not a canonical identifier; however, in accordance with implementations discussed elsewhere herein, comments can be retrieved from across multiple properties for the content item by first determining a canonical identifier corresponding the content parameter.

The application B further includes a comment generator 582 which provides the functionality of the aforementioned comment entry field 554, to allow the user to generate a new comment related to the content item. The comment generator 582 uploads data defining the new comment to a comments server 588, which stores the data in a comments data storage 589. A comment retrieval module 583 is configured to retrieve comments related to the identified content item from the comments server 588, which in turn serves comments from the coments data storage 589. A graphical user interface 584 is presented to the user, an example of which is shown by the view 550 at FIG. 5C.

In some implementations, the aforementioned API call may additionally pass information to allow the user to return to the original application A (e.g. local URL information for the application A). The application B may thus present a feature which opens the previous application A (e.g. a “back” button utilizing the local URL information). This can be useful for returning the user to a prior application in an easy fashion.

FIG. 6 conceptually illustrates a post about a content item, and a subsequent post about the earlier post. A content item 600 has an associated URL 602. A post 604 includes post content 608 which defines the information that will be displayed when the post 604 is displayed. The post content 608 may include various information, including text entered by the user, an attached image/audio, links, etc. In the illustrated example, the post content 608 includes the URL 602 of the content 600. The post 604 also include metadata 610. In the metadata 610, a tag is defined by a canonical URL which has been determined based on identification of the URL present in the post content 608. The canonical URL may be the same as or different than the URL 602. Thus, the post 604 is tagged with a canonical URL identifying the content 600.

In one scenario, the post 604 may be shared with others through the generation of a later post 612. The post content 614 of this later post 612 may thus include the URL 606 of the earlier post 604. The post metadata 616 of the later post 612 may also include a tag identifying the post 604, which can be the URL 606 of the post 604 or a canonicalized version of it.

When a search is performed for posts related to the content 600, posts tagged with the canonical ID associated with the content 600 are retrieved. These will include the post 604, but not the post 612, as it is not tagged as such. In this manner, posts about the content can be retrieved apart from later posts that reshare an earlier post about the content. This can be desirable, for example, when serving a page which features the content 600, for which it is not necessary to retrieve additional posts which are reshares of existing posts about the content. On the other hand, it may be desirable to understand or present a given post along with all of its reshares, in which case the presently described configuration facilitates retrieval of posts tagged with the URL 606 of the post 604, so as to include post 612 which is a reshare of the post 604.

FIG. 7A illustrates an interface for moderating comments about a content item by an owner of the content item. The web page 700 presents content item 702. In the illustrated view, the user is logged in as the owner of the content item. The illustrated page 700 can be of a website where content items can be created, uploaded, and edited by content owners, as well where such content items are hosted and made available for download or consumption (e.g. viewing an image or video, listening to an audio file, etc.) by other users. In a box 704, the owner can enter text to create a new comment. Comments relating to the content item 702 are displayed in a comments display region 710.

In some implementations, a content owner can be provided with options to moderate comments. For example, a content owner may predefine settings governing how new comments are handled. One possible setting would configure comments to be automatically approved for display unless the owner indicates otherwise. Another possible setting would configure comments to be not approved unless the owner specifically approves them for display.

In the illustrated implementation, a notification 706 informs the owner that there are comments awaiting approval. By clicking on the button 708, the owner is able to access the comments 712 which have yet to be approved. These comments will not be displayed to other users accessing the page 700 unless specifically approved by the owner. The owner may indicate approval of the comment for display by activating button 714. Alternatively, the owner may delete a pending comment by activating button 716.

It will be appreciated that at the time a comment about a content item is generated, it can be determined whether or not the content item has an identifiable owner. If an owner can be identified, then the settings predefined by the owner for the specific content item can govern the handling and display of the new comment on the content item's webpage. However, if no owner exists, then the comment can be included for display alongside other comments on the content item's webpage. Whether or not the comment is actually displayed when a given user accesses the content item's webpage may depend on other factors, as described elsewhere herein, e.g. recency, ranking, etc.

FIG. 7B illustrates an interface for moderating comments which have been posted relating to a content item, in accordance with an implementation of the disclosure. A comments management view is shown for allowing an owner of a content item or page, for which comments may be posted by third-party users, to moderate the display of such comments. In the illustrated implementation, a view selection portion 720 of the interface facilitates selection of which comments to display in a comments display region 730 of the interface. By way of example, a button 722 can be selected to display all comments which are available for viewing by the owner. As discussed elsewhere herein, it should be appreciated that not all comments which reference the content item or page of the owner will necessarily be available for viewing by the owner. For example, a comment by a user may not be available for viewing by the owner if the comment is not publicly shared, but instead shared with selected users (excluding the owner), e.g. individuals or subgroups in the commenting user's social graph. Thus, selection of the button 722 will not cause display of such privately shared comments, but will facilitate display of comments to which the owner does have access.

A button 724 can be selected to cause display of comments which have yet to be approved by the owner for display on the owner's page. The number of such comments which are awaiting approval may be displayed on or alongside the button 724. In the illustrated implementation, there is one comment awaiting approval by the owner. A button 726 can be selected to display comments which have been approved for display on the owner's page. In the illustrated implementation there are 23 comments which have been approved. A button 728 can be selected to cause display of comments which have been disapproved from being displayed on the owner's page. In the illustrated implementation, there are three comments which have bee disapproved. It should be appreciated that a comment that has been disapproved for display on the owner's page may nonetheless still be displayed in another context, e.g. in the social networking stream of the commenting user or that of users in the commenting user's social graph.

In the illustrated implementation, in the comments display region 730, a comment 732 is shown. Comment 732 is indicated as awaiting approval by the owner. The owner may select a button 734 to approve the comment 732 or a button 736 to disapprove the comment. If approved, then the comment 732 will be available for display on the owner's page, and may or may not be displayed for a given user accessing the page depending upon various factors are described elsewhere. If disapproved, then the comment 732 will not be available for display on the owner's page. Below the comment 732, a comment 738 is shown. The comment 738 is indicated as having already been approved on a specified date.

Additionally, a sorting menu 740 facilitates selection of a method for sorting the display of comments in the comments display region 730. For example, the comments may be sorted by recency of posting or other activity related to the posting (e.g. response posted). Comments may also be sorted based on activity relating to the comment (e.g. recent replies to a specific comment, resharing of the comment), social graph data of the user, etc.

The foregoing implementation has generally been described to facilitate the owner's ability to approve and disapprove comments for display on the owner's page. In such an implementation, comments may be pre-filtered, such that a comment is not available for display on the owner's page unless the owner expressly approves the comment. However, in another implementation, comments can be post-filtered, wherein a comments is available for display on the owner's page unless the owner expressly disapproves the comment. For the various implementations, the comments management view can include different or additional options. For example, there may be provided an option to show “unread” comments, that when selected, causes display of comments which have not been viewed by the owner. Whether a comment has been viewed by the owner may be determined based on, for example, the owner having clicked on the comment or otherwise selected the comment for viewing. Another option may cause display of “new” comments, which are comments that have been received since the last time the owner logged in and accessed the comments management view.

FIG. 8A illustrates a method for handling the display of comments on a page. At method operation 800, a page request is received. At method operation 802, a canonical ID is determined for the requested page. At method operation 804, a search is conducted for comments which have been tagged with the canonical ID, and these comments are retrieved for possible display. At method operation 806, characteristics of the viewer are identified. For example, if it is determined that the viewer is an owner of the requested page, then at method operation 808, an owner's view is displayed to the user. The owner's view can be similar to that described with reference to FIG. 7A or 7B, providing the owner with privileged features including the ability to approve comments for display or delete comments.

With continued reference to FIG. 8A, at operation 806, if it is determined that the viewer is a third party, then at operation 810, a filtering is applied to the retrieved comments based on predefined settings which have been set for the page. If no filtering is to be applied, then at operation 812, all retrieved comments are made available for display. If post-filtering is applied, then at operation 814, all comments are made available for display unless they have been disapproved by the page owner. And if pre-filtering is applied, then at operation 816, only those comments which have been positively approved by the owner are made available for display.

At operation 818, the comments which are available for display are ranked based on various factors, including characteristics of the viewer, characteristics of the authors of the comments, and characteristics of the comments. By way of example, these may include various specific factors, including: recency of a comment, ratings of a comment, responses to a comment, length of a comment, keywords found in comment, geographic location of the viewer, geographic location of a comment author, whether or not a comment author is in a social graph of the viewer, etc. Various weights can be applied to the various factors to produce an overall score for each available comment. The available comments may thus be ranked based on their overall scores. At operation 820, the comments are displayed on the requested page based on their ranked order.

FIG. 8B illustrates a method for displaying posts on an owner's page based on predefined moderation settings, in accordance with an implementation of the disclosure. At operation 830, a stream of post data items associated with a content item is identified. The stream of post data items is typically presented on a web page in conjunction with the content item. An owner of the web page is able to moderate the display of post data items in the stream in accordance with methods described herein. At operation 832, a moderation setting is defined by the owner for the stream. Three choices are provided for the owner in this regard: (1) no filtering (reference 834), in which post data items, e.g., all post data items, are available for display in the stream; (2) post-filtering (reference 836), in which post data items are available for display in the stream unless the owner indicates otherwise through a disapproval/deletion mechanism; or (3) pre-filtering (reference 838), in which the owner approves post data items that are available for display in the stream.

At operation 840, a user accessing the owner's page is identified. Identification of the user may be facilitated via various systems for which the user logs in to establish their identity, e.g. a website which includes the owner's page, a social network, an e-mail service, etc. At operation 842, the setting for the stream shown on the owner's page is determined. As noted above, the stream can be configured to have no filtering, post-filtering, or pre-filtering applied. If no filtering is applied, then at operation 844, the metadata for all posts is retrieved for consideration. If the stream is configured to be post-filtered, then at operation 846, metadata for all posts except those which have been expressly disapproved by the owner is retrieved for consideration. If the stream is configured to be pre-filtered, then at operation 848, the metadata for posts which have been expressly approved by the owner is retrieved.

At operation 850, the posts are ranked based on the retrieved post metadata and characteristics of the user. It will be appreciated that the post metadata for a given post may include any of various kinds of information about the post, e.g. date/time of creation, author's user ID, indications of approval by other users (likes, +1's, thumbs up, etc.), inclusion of links or other content items, or any other information which may be relevant for ranking purposes. The characteristics of the user can include any of various information that be determined obout a given user, e.g. geographic location, social graph data, etc. The post metadata can be considered in combination with the user characteristics. For example, posts that are authored by or which have received an indication of approval by others in the user's social graph may be prioritized for display to the user. It will be appreciated that consideration of factors based on the post metadata and user characteristics can be based on a weighted scoring system, with various weights applied to the various factors under consideration, so as to yield an overall score for each post. The ranking of the posts can then be based on the overall score for each of the posts.

At operation 852, the post content (e.g. text and content items included in the post) for the posts to be displayed is retrieved. At operation 854, the posts are displayed in accordance with their ranking. Optionally, at operation 856, the user may provide input which affects the ranking, e.g. requesting sorting of the posts according to a specific sorting profile.

FIG. 9 illustrates a system for filtering the display of comments on a property webpage, based in part on social network data. A social network server 900 accesses data from an accounts storage 902 containing user data on the social network. An API 904 is provided, by which social network data can be requested and accessed. A login module 906 logs the user 908 into the social network.

The property server 910 includes a login module 914 for logging in users. Owner account information is stored in owner accounts storage 912. For example, an owner 922 is shown logging on to the property. The property server 910 hosts a webpage requested by the user 908. In reponse to the request for the webpage, comments retrieval module 916 retrieves relevant comments from the content data storage 920. A filtering module 918 filters the comments according to various criteria, as has been discussed above. The filtering process can include accessing the API 904 of the social network to retrieve social graph data of the user 908, as well as social graph data of authors of comments.

FIG. 10 conceptually illustrates the display of a private post based on the user viewing a content page, in accordance with implementations of the disclosure. A content page 1000 is shown as viewed by a user A who is logged in. The content page 1000 includes a content item 1002. The user A creates a new post 1004 that is private (or not designated as public) and shared with users who are connected to user A in some fashion, e.g. users who are part of user A's social graph or part of a subgroup of users in user A's social graph. In the illustrated embodiment, user B is part of user A's social graph. Hence, when user B is logged in and views the same content page, then the content page 1006 presented to user B includes access to the private post 1004 created by user A. User B may choose to reply to user A's post 1004, and therefore generate a reply post 1008. This reply post can be displayed on the content page 1000 presented to user A, as user A is part of user B's social graph.

However, because the post 1004 is not a public post, but a private post shared with a limited group of users, the post 1004 is not viewable in the public view of the content page (no user logged in), as shown at reference 1010. The private post 1004 would also not be available for display to another logged in user who is not part of the group of users with whom the post 1004 was shared. Moreover, the post 1004 is also not available for viewing when the owner is logged in to the content page, as shown at reference 1012.

FIG. 11 conceptually illustrates the posting of a public post to a social network, in accordance with implementations of the disclosure. A social network page 1100 of a user A is shown. The user A generates a new public post 1102 and shares it with users B, C, and D. The post 1102 includes a reference 1104 to content on a content page 1114 that is created or owned by an author 1124, and is also tagged with a content ID based on identification of the content reference 1104. The post 1102 is displayed in the personal social network feed or stream 1101 of user A, and also in those of users B, C, and D, with whom the post 1102 has been shared. Thus, the post 1102 appears on the social network pages 1108, 1110, and 1112 of users B, C, and D, respectively.

As the post 1102 is a public post, it may also be available for display on the author's 1124 content page 1114, provided the content page 1114 includes an active stream for displaying posts. The content page 1114 includes an authorship tag 1120 that identifies the author 1124 as the author of the content page 1114. Based on identification of the author 1124 according to the authorship tag 1120, a notification can be sent to the author 1124, informing the author of the creation of the posting 1102. The authorship tag can include any of various kinds of information facilitating notification of the author, e.g. an e-mail address, a phone number, a network address or domain, a username (e.g. a social network username, messenger service username, chat service username, or username on another type of property), or any other type of information specifying a destination for a notification or providing information from which a notification may otherwise be generated.

In accordance with the present disclosure, the author 1124 can be notified when a public posting is generated that is about the author's content. The notification can occur via a messaging service 1122, e.g. an e-mail service, a social network, a mobile messaging service, a private message service of a website, etc. By notifying the author of a public post that is about their content, the author is afforded the opportunity to moderate the post if it may appear in a stream on the author's page, and also the opportunity to reply to the post and thus participate in the conversation about their content that is occurring in the context of the post. In the illustrated implementation, the author 1124 is notified of the post 1102 which appears on the author's content page 1114. The author 1124 responds to the post 1102 by posting a reply post 1118 on the content page 1114, the reply post 1118 being also propagated to the stream 1101 of the social network page 1100 of the user A, as well as those of the users B, C, and D.

It should be appreciated that an author may also be referred to as an owner or other designated title to whom content can be attributed, and such can be not just a person, but a group, organization, or any other type of entity that may be attributed with authorship or ownership of content. Identification of an author or owner for purposes of the present disclosure may not necessarily require identification of an actual person or entity's proper name, but may simply entail determination of identifying information that attributes the content or page to a known person or entity, and which may be used to notify said person or entity that a post has been generated about their content/page. Additionally, it will be appreciated that there may be a plurality of authors or owners associated with a given content item. In various implementations, some or all of the authors/owners can be notified, conditional upon preferences defined individually or collectively.

Implementations of the present disclosure provide for the owner of content or a content page to be notified when a post is generated about their content. It should be appreciated that the location of the post and the location of the content can be on unrelated properties, e.g. on different web pages that do not share a common domain, on different networks, different web sites, etc. In some implementations, the post is generated on a social network, whereas the content is located on a content web site that does not share a common domain with the social network.

FIG. 12 illustrates a method for notifying an author of a new post relating to their content item, and for displaying the new post as part of the content item's posting stream. At operation 1200, a request is received to generate a new post. The new post can include a content item or a reference to the content item or a page including the content item, as well as other post content. At operation 1202, it is determined whether the post is a public post or not. If so, then at operation 1204, the post content is analyzed to identify the content item. At operation 1206, the author of the content item is identified. In some implementations, the author can be identified through detection of an authorship tag associated with the content item or page which includes the content item.

At operation 1208, it is determined whether the author is currently online. The online availability of the author may be determined based on checking the login status of the author on a relevant system, e.g. social network, content website, or other website. If the author is determined to be online, then at operation 1210, an online notification is displayed to the author. For example, a pop-up display, an alert bar, or some other type of visual notification mechanism may be displayed to the author during the author's online session on the social network or website. The notification may also include playback of an audio alert sound. The notification alerts the author to the fact of a new public post having been generated which relates to the author's content. In addition to the online notification, at operation 1212, an offline notification may be sent to the user, e.g. an e-mail, private message, mobile alert, etc. It will be appreciated that if at operation 1208 the author is determined not to be online, then at operation 1212, the offline notification is sent. As with the online notification, the offline notification provides information regarding the newly generated post that relates to the author's content.

In some implementations, notifications (both online and offline) can include interactive elements in addition to alerting the author about a new post. For example, a notification may include a preview of the post's content, along with selectable options for approving or disapproving the post. In some implementations, the notification includes a link for navigating to a management page through which the author may moderate the post. The notification may also include a link to the original context of the post, e.g. to the social network page of a user who first posted the comment to their social network stream.

FIG. 13 illustrates a system for notifying an author of a newly generated post which references or includes content of the author. Various content pages 1300 are shown which contain content that may be included or otherwise referenced in posts. A given content page can include an authorship tag 1302 which identifies an author of the content page. A given content page may also include a post widget 1304 configured to manage the display of posts on the content page as well as provide a mechanism for creating new posts. An indexer 1306 indexes the content pages, storing information to a registry 1310. For a given content page, the indexer 1306 may store various kinds of information, including the URL of the content page, an identified author associated with the content page, an address for notification of the author (e.g. based on reading the authorship tag 1302 of the content page), and a content ID that can be utilized to tag a post which includes a reference to the content page. A content ID generator 1308 generates the content ID for a given content page.

A post data storage 1312 stores data defining posts. As noted, posts can be generated from a post widget included in a content page. Posts may also be generated from a social network 1314, which includes a post generator 1316 for generating new posts. A notification module 1318 is configured to include an author identification module 1320 for identifying an author of a content page referenced by a post. Based on identification of the author, the notification module 1318 activates either or both of an online notification mechanism if the author is online, and an offline notification mechanism, e.g. accessing a communication service 1322 to send a message to the author 1324. The post widget 1304 can be similarly configured to provide for notification of an author of content referenced by a post.

In various implementations, the identification module 1318 can be configured to determine authorship in various ways. For example, as has been described, authorship can be determined by accessing and reading a file referenced by the post to identify an authorship tag that identifies the author and provides information relevant to facilitate notification of the author. In another implementation, authors or owners of content can register their content via a registration service 1326. The registration service 1326 allows content owners to associate ownership and contact information (e.g. e-mail address, phone number, username, etc.) with a reference to their content in the registry 1310. The identification module 1318 reads the relevant ownership and contact information from the registry 1310 for a given content item, and this information is utilized by the notification module 1318 to trigger sending of a notification to the identified owner of the content.

FIG. 14 illustrates a flow of comments amongst a news cluster. A news cluster 1400 is defined to include a number of news articles 1402, 1404, and 1406, each of which relates to the same topic. The particular news articles which are included in the new cluster can be determined based on analysis of the content of various news articles to, for example, identify keywords, image content, etc. In some implementations, a level of similarity between news articles is determined, and those news articles having a level of similarity above a predefined threshold are included in a common news cluster.

In the illustrated implementation, the article 1404 is presented on a page 1408 with user-generated coments displayed below the article. A comment 1410 is generated by a user in response to the article. However, as the article 1404 is part of the same news cluster as article 1406, the comment 1410, in accordance with mechisms described herein, can appear in the comments section that is displayed when the article 1406 is presented on a page 1412. Similarly, a comment 1414 that is generated in response to the article 1406 on the page 1412, may appear in the comments section of the page 1408.

The articles 1402, 1404, and 1406 are different from each other. But because they have been identified as part of the same news cluster, comments relating to the articles may be tagged with a common identifier. Then when one of the articles is displayed, a search can be performed for comments which have been tagged with the common identifier, thereby retrieving comments which have been generated for any of the articles in the news cluster. In this manner, comments from any of the articles in the news cluster are made available for display when one of the news articles is presented on a page.

FIG. 15 illustrates various identifiers defined for objects relating to posts, in accordance with implementations of the disclosure. A post 1500 is defined to include a content item 1502 (e.g. a video) and text 1504. For each of these items, a unique ID can be determined. For example, the content item 1502 can have an ID1, the text 1504 an ID2, and the post 1500 an ID3. The post 1500 can be tagged with each of these ID's, i.e. post 1500 is tagged with ID1, ID2, and ID3.

One response to post 1500 is a post 1506, which includes text 1508. The text 1508 can be assigned an ID4, and the post 1506 assigned an ID5. The post 1506 can thus be tagged with ID3 (the ID of the post to which post 1506 responds) as well as ID4 and ID5.

Another response to post 1500 is a post 1510, which includes a content item 1512. The content item 1512 can be assigned an ID6 and the post 1510 assigned an ID7. The post 1510 can be tagged with the ID3 (the ID of the post to which post 1510 responds, as well as ID6 and ID7.

A response to the post 1510 is a post 1514, which includes text 1516. The text 1516 is given ID8 and the post 1514 is given ID9, so that the post 1514 is tagged with ID7 (the ID of the post to which post 1514 responds) and ID8 and ID9.

One may reshare a post or portions thereof. For example, a post 1518 reshares the content item 1502, but not the text 1504 of post 1500. The post 1518 is given an ID10. The post 1518 is therefore tagged with the ID1 (ID of the content item 1502 being reshared) and ID10.

A post 1520 reshares the text 1504 but not the content item 1502 of the post 1500. The post 1520 is given an ID11. The post 1520 is thus tagged with ID2 (the ID of the text 1504 being reshared) and the ID11.

A post 1522 reshares the post 1500 in its entirety. The post 1522 thus includes the content item 1502 and the text 1504. The post 1522 is given ID12. The post 1522 is tagged with ID3 (the ID of the post 1500 being reshared, and the ID12.

It should be appreciated that a reshare of a post may occur when a user endorses or indicates approval of the post, e.g. by selecting a button to indicate that they “like” or “+1” the post, give it thumbs up, etc. The endorsement action can be shared to the user's social graph, and may appear in their stream of posts as a new post indicating that the user approved or endorsed the earlier post. The new post may contain some or all of the earlier post or a link to the earlier post, and thereby functions to reshare the earlier post.

As posts are tagged with various ID's, searches can be conducted based on the tags to retrieve posts which relate to a particular content item, text, or post.

As discussed herein, users that generate posts or content may receive notifications regarding activity related to such posts or content. In some implementations, such a notification can be defined to be sensitive to the recipient's perceived location (e.g. website or other property) of interaction—that is, the location at which a user, who receives the notification, originally generated a post or content for which the notification is being sent. The notification can be defined to appear as being sent from the location. With reference to FIGS. 16A and 16B, an example scenario involving posts by different users at different locations and the resultant notifications the different users are shown, illustrating principles in accordance with implementations of the disclosure.

At FIG. 16A, a view 1600 of a content website is shown (e.g. a web page view). A user “Bob” is logged in to the content webite (ref. 1602). A video 1604 has been uploaded to the content website by a user “Alice.” Bob sees Alice's video 1604 and creates a comment 1606 related to the video 1604 at the content website. Bob's comment 1606 is displayed on the content website, and is also shared to Bob's social graph as defined by a social network.

The view 1620 (e.g. a web page view) of the social network shows a user “Christie” logged in to the social network (ref. 1622). In the illustrated implementation, a post generation interface 1624 is provided in the view 1620 for generating new posts to the social network. Christie is a member of Bob's social graph, and therefore, Bob's comment 1606 on Alice's video 1604 appears in a recent activity feed for Christie on the social network as a post 1626. The post 1626 indicates that Bob has commented on Alice's video, provides the content of Bob's comment (“Nice video!”), and further includes a link 1628 to Bob's comment on the content website. The post 1626 additionally includes a viewer 1630 configured to display Alice's video within the context of the post 1626 on the social network. Christie generates a post 1632 on the social network in reply to Bob's post 1626. Christie's post 1632 is displayed not only on the social network, but can also be displayed at the content website, e.g. as comment 1608 in Bobs view 1600 of the content website.

The view 1640 of the content website shows a user “David” logged in to the content website, and also viewing Alice's video (ref. 1644). Bob's comment appears at ref. 1646, and Christie's reply to Bob's comment appears at ref. 1648. David replies to Christie's comment, generating a comment 1650 at the content website. David's comment 1650 additionally references/tags Alice and Bob (ref. 1652). David's comment 1650 appears in Bob's view 1600 of the content website at ref. 1610, and also appears in Christie's view 1620 of the social network, at ref. 1634.

The aforementioned activity by the various users of the content website and the social network can result in various notification activity. The posting of Bob's comment 1606 results in notification activity “A”; the posting of Christie's post 1632 results in notification activity “B”; and the posting of David's comment 1650 results in notification activity “C.” The various notification activity A, B, and C are conceptually illustrated and described with reference to FIG. 16B.

When Bob's comments on Alice's video on the content website 1660, a notification 1664 is sent to Alice, indicating that Bob has commented on the video. The notification 1664 is defined from the content website 1660, and may include contents of Bob's comment (“Nice video!”) as well as a link to view the comment at the content website 1660.

When Christie posts her reply to Bob's comment at the social network 1662, a notification 1666 is sent to Alice from the content website 1660 indicating that Christie has commented on Alice's video. The notification 1666 may include the contents of Christie's comment (“That's neat!”), as well as a link 1668 to view the comment on the content website 1660. Additionally, Christie's post results in a notification 1670 being sent to Bob, indicating that Christie has replied to Bob's comment on Alice's video. Since Bob interacted (commented) at the content website 1660, the notification 1670 is defined as being from the content website 1660, and may include a link to view Christie's reply at the content website 1660, even though Christie generated the reply at the social network 1662.

When David replies to Christie's comment at the content website, a notification 1672 from the content website is sent to Alice, indicating that David has commented on Alice's video. Christie receives a notification 1674 indicating that David has replied to her post. However, because Christie posted at the social network 1662, the notification 1674 resulting from David's reply is defined as being sent from the social network to Christie, even though David replied to Christie at the content website. The notification 1674 can include a link to view David's reply at the social network. Alice additionally receives a notification 1676 from the content website indicating that David has referenced/tagged Alice in a comment. Bob also receives a notification 1678 from the content website indicating that David has referenced/tagged Bob in a comment.

As demonstrated, a system can be configured to determine which location (e.g. website, system, property, application, etc.) each user thinks they are on, and route notifications to each user based on the system where the user believes that they are. A notification from a social network would, e.g., be inside an e-mail from the social network, and would link to a social network page, whereas a notification from a content site would be in an e-mail from the content site, and would link to a content viewing page. It will be appreciated that a single action might lead to notifications reaching different people from different sources, since the source depends on the receiver's perspective. In sum, notifications can be routed from various notification sources based on the receiver's perceived application.

In addition to notifications which can appear to arrive from multiple sources, there are several possibilities for determining a best source, some examples of which are provided herein without limitation. For example, when a user interacts with a particular comment thread (a post+comments, a.k.a. a comment on some content plus its replies), the location from which each such interaction occurs can be identified, and that information stored along with the information about the user's interaction.

If a user has already interacted with a comment thread, then the source location may be considered to be the first (alternatively, the most recent) location where the user interacted with the comment thread. The first location may be advantageous because the first location is stable and will not change over time, even if the user interacts with the thread in multiple locations, which is predictable for the user. Whereas, utilizing the most recent location can be advantageous in terms of responding to user behavior.

If a user has not already interacted with a comment thread, then a default source location can be defined. Alternatively, the source location may be considered to be the location at which the parent interaction (i.e., the post itself) occurred.

By routing notifications from different sources depending upon the recipient's perceived location of interaction, the notification methods and system described herein allow users to feel like they are using separate apps, even as the data defining posts/comments/etc. moves smoothly between them.

Methods and systems for moderating the display of new comments/posts relating to a content item have been discussed above. In further implementations, a comments stream can be presented in one of two views: a user view, which is presented to viewers of the content; and an inbox view, which is presented to moderators to make decisions about comments/posts not visible to general viewers. An ordinary user, accessing the system, will be presented with the user view. An authorized moderator (e.g. the owner of the stream and content item, or their delegates, i.e. any plurality of individuals, circles, or communities, authorized as additional moderators) can additionally be provided with controls which allow them to reject any content shown, or to access an inbox view of items which are not yet shown but which the moderator may either approve (making them visible to ordinary users) or reject (discarding altogether). Additionally, a warning indicator can be provided if an item in the inbox view may require the moderator's attention. The inbox view may be further subdivided into multiple views or portions, each corresponding to a different reason why something is in the inbox and not shown to users.

In order to achieve the foregoing, certain state information is maintained for each comment. Specifically, a moderation state, which represents decisions made by a human moderator, and a spam state, which represents decisions made by a spam/abuse system, are defined. Four different moderation states are defined: NEW, HOLD, APPROVED, and REJECTED. Three different spam states are defined: not spam, possibly spam, and definitely spam. The spam states identify the likelihood of the comment to be illegitimate or legitimate. Though three spam states are specifically described in the present implementation, it will be appreciated that in other implementations, other states are possible. For example, there may be any number of spam states (at least two states required), or a continuous range of spam states. Spam states may be defined by or with reference to a numerical legitimacy score which indicates a likelihood that a given comment is spam or not spam (illegitimate or legitimate). Furthermore, spam states may be defined by particular ranges of such a numerical score. The moderation states and spam states are further described with reference to FIG. 17A, illustrating a method for handling and moderating a new comment, in accordance with implementations of the disclosure.

At operation 1700, a new comment is generated. At operation 1702 it is determined whether the new comment is definitely spam. If yes, then at operation 1704, the comment is removed from the system; if no, then at operation 1706, it is determined if the comment originates from a moderator or an approved user. If yes, then at operation 1708, the comment is marked as APPROVED. An owner may designate any listing of people (individual users, circles, communities, etc.) as additional moderators. The owner may also designate any listing of people as automatically approved. Any comments by these users are assigned the APPROVED state. This can override rules described below, which mark comments as HOLD, as well as spam and abuse determinations, and therefore such designated users are trusted users.

If at operation 1706, it is determined that the comment does not originate from a moderator or approved user, then at operation 1710, it is determined whether the comment originates from a banned user. If yes, then at operation 1712, then the comment is marked as REJECTED. A moderator may designate certain users as banned, and any comments by these users are assigned the REJECTED state.

If at operation 1710 it is determined that the comment does not originate from a banned user, then at operation 1714 it is determined whether a hold rule applies. If yes, then at operation 1716, the comment is marked as HOLD. A comment marked as HOLD has not been acted on explicitly by a moderator, and it is being held for moderation because of a pre-specified rule determined by the moderator. (Further examples of hold rules are provided below.) A comment marked HOLD is not shown in the user view, but is shown in the inbox view (ref. 1724) to allow the moderator to decide whether to mark the comment as APPROVED or REJECTED (ref. 1726).

If at operation 1714 it is determined not to apply a hold rule, then at operation 1718, the comment is marked as NEW. A comment marked as NEW has not been acted on by a moderator yet. At operation 1720, it is determined whether the comment is possibly spam. If it is not spam, then at operation 1722, the comment is shown in the user view. If the comment is determined to be possibly spam, then it is hidden from the user view, and shown in the inbox view (ref. 1724), for eventual moderator action marking the comment as APPROVED or REJECTED.

FIG. 17B illustrates a flow diagram indicating a method for determining whether to display or hide a comment from a user view, in accordance with implementations of the disclosure. At operation 1730, the moderation state of the comment determined. If the moderation state is NEW, then at operation 1732, it is determined whether the comment is possibly spam. If no, then at operation 1734, the comment is displayed in the user view; if yes, then at operation 1736, the comment is hidden from the user view.

If the moderation state of the comment is APPROVED, then at operation 1734, the comment is shown in the user view, regardless of its spam state.

If the moderation state of the comment is REJECTED, then at operation 1738 it is determined whether the current user viewing the user view is the author of the comment. If yes, then the comment is displayed in the user view (ref. 1734); if no, then the comment is hidden from the user view (ref. 1736). A comment marked as REJECTED has been rejected by a moderator (either explicitly, or because the comment's author is a banned user). This comment is generally not shown in either the user view or the inbox. However, when the author of this comment views it, they should still see it in the user view. In this manner, the author of rejected content is not given any visible indication that their content has been rejected. This can be advantageous because users whose content is rejected can become angry and quickly attempt to take revenge, e.g. by creating new dummy accounts and posting further bad content. However, when they are banned in the aforementioned manner, then it simply appears to them that they have posted successfully, but nobody is engaging with them.

Various implementations may include additional features or modifications to the foregoing. For example, an option can be provided to hold all comments, wherein all new comments are marked as having the HOLD state, unless another rule overrides this (e.g. approved user or banned user).

Additionally, the owner may provide a list of words and/or phrases which are defined as bad words. If a comment includes content approximately matching any of these bad words, it will be placed in a HOLD state instead of a NEW state. Various semantic matching techniques may be utilized to determine whether a given comment includes content approximately matching a predefined bad word or phrase.

It is noted that a comment may have replies which are in a different state. It is generally contemplated that if a comment has a child which should be visible in the inbox view, then the comment itself is shown there as well, for clarity. For example, if a comment is APPROVED, and someone makes a reply to it which is marked HOLD, then the comment, but not its reply, will be shown in the user view; whereas in the inbox view, the comment and the reply will both be shown, with an indicator that the comment itself is already approved but its reply is not.

Additionally, when an existing comment is modified, if it was previously approved then it may proceed through the above-described process for determining its state. However, if it was previously in any other state, then its state is unchanged. This configuration prevents someone whose comment is rejected from spamming the moderators by continuously editing the comment and sending it back for re-evaluation again.

FIG. 18 is a schematic diagram of a computer system for implementing implementations of the present disclosure. It should be appreciated that the methods described herein may be performed with a digital processing system, which in one implementation may be a conventional, general-purpose computer system. Special purpose computers, which are designed or programmed to perform only one function, may be used in the alternative. The computing device 1950 includes a processor 1954, which is coupled through a bus to memory 1956, permanent storage 1958, and Input/Output (I/O) interface 1960.

Permanent storage 1958 represents a persistent data storage device, e.g., a hard drive or a USB drive, which may be local or remote. Network interface 1962 provides connections via network 1964, allowing communications (wired or wireless) with other devices. It should be appreciated that processor 1954 may be embodied in a general-purpose processor, a special purpose processor, or a specially programmed logic device. Input/Output (I/O) interface 1960 provides communication with different peripherals and is connected with processor 1954, memory 1956, and permanent storage 1958, through the bus. Sample peripherals include display 1972, keyboard 1968, mouse 1970, removable media device 1966, etc.

Display 1972 is configured to display the user interfaces described herein. Keyboard 1968, mouse 1970, removable media device 1966, and other peripherals are coupled to I/O interface 1960 in order to exchange information with processor 1954. It should be appreciated that data to and from external devices may be communicated through I/O interface 1960. Implementations of the disclosure can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wired or a wireless network.

Implementations of the present disclosure can be fabricated as computer readable code on a non-transitory computer readable storage medium. The non-transitory computer readable storage medium holds data which can be read by a computer system. Examples of the non-transitory computer readable storage medium include permanent storage 1958, network attached storage (NAS), read-only memory or random-access memory in memory module 1956, Compact Discs (CD), Blu-Ray™ discs, flash drives, hard drives, magnetic tapes, and other data storage devices. The non-transitory computer readable storage medium may be distributed over a network-coupled computer system so that the computer readable code is stored and executed in a distributed fashion.

Some, or all operations of the method presented herein are executed through a processor. Additionally, although the method operations were described in a specific order, it should be understood that some operations may be performed in a different order, when the order of the operations do not affect the expected results. In addition, other operations may be included in the methods presented, and the operations may be performed by different entities in a distributed fashion, as long as the processing of the operations is performed in the desired way.

In addition, at least one operation of some methods performs physical manipulation of physical quantities, and some of the operations described herein are useful machine operations. Implementations presented herein recite a device or apparatus. The apparatus may be specially constructed for the required purpose or may be a general purpose computer. The apparatus includes a processor capable of executing the program instructions of the computer programs presented herein.

Further shown are a plurality of other devices, storage, and services that may be connected to network 1964. Network 1964 can be, for example, the Internet. The Internet is interconnected with a plurality of devices, including cloud storage servers, cloud logic servers, user interface devices, etc. Some devices that can communicate with the Internet access services on various cloud logic servers and cloud storage can include, e.g., tablet computers, smart phones, laptops, desktop computers, television systems, and the like. The devices that can communicate with each other require at least a processor, and a display for presenting user interface views from selected programs and code that render the user interfaces. The user interface can be provided through keyboard entry, text entry, voice entry, gesture entry, and combinations thereof.

The user interfaces can be presented in browsers of the various devices, can interpret HTML code, can render video, can communicate over the Internet by way of wireless communication, can render Flash video data, and the like. All of these devices, hardware implementations, and code are configured for enabling the interfacing and interaction with the social network, and the users of the social network, and users on various websites connected to the Internet. The interaction, through social networks will enable electronic messaging regarding current information, shared interests, chat communication, video communication, and general posting, interests, and relationship management. Broadly speaking, a social network is a site that allows at least two people or entities to communicate with one another and share at least one piece of data.

Although the foregoing implementations have been described with a certain level of detail for purposes of clarity, it is noted that certain changes and modifications can be practiced within the scope of the appended claims. Accordingly, the provided implementations are to be considered illustrative and not restrictive, not limited by the details presented herein, and may be modified within the scope and equivalents of the appended claims. 

What is claimed is:
 1. A method comprising: receiving a request from a user to generate a first post data item in a group of post data items at a first location that corresponds to a social network page; providing for presentation of the first post data item with the group of post data items at a second location that corresponds to a content page that does not share a domain with the social network page; receiving a request from another user to generate a second post data item in the group of post data items at the second location, the second post data item being in reply to the first post data item; identifying a destination associated with the user for notification about the second post data item; determining whether the group of post data items at the first location or the second location was interacted with by the user; and providing, by a processor of a server and in association with the destination, a notification for the user, wherein the notification identifies the second post data item and a reference to the group of post data items at the first location or the second location based on the determination of whether the group of post data items was interacted with by the user at the first location or the second location.
 2. The method of claim 1, wherein presenting the first post data item at the second location includes accessing a social graph of the user from whom the request to generate the first post data item is received, and identifying a second user as a member of the social graph of the user, the second user identified as accessing the second location.
 3. The method of claim 1, wherein the notification is defined by one or more of an e-mail, a private message, or an alert.
 4. The method of claim 1, wherein the first post data item is generated in reply to a third post data item, the third post data item being originally generated at the second location and presented at the first location.
 5. The method of claim 1, wherein the notification includes a link to the second post data item presented at the first location.
 6. The method of claim 1, wherein identifying the destination for notification associated with the first post data item includes accessing a notification tag associated with the first post data item.
 7. The method of claim 1, wherein the notification provides access to a moderation interface for approving or rejecting the second post data item for display at the first location.
 8. The method of claim 7, wherein when the second post data item is rejected, then the second post data item is not displayed at the first location except when the user accessing the first location is identified as the author of the second post data item.
 9. The method of claim 1, wherein the first location or the second location defines a service.
 10. The method of claim 1, wherein the second post data item is a direct reply to the first post data item.
 11. The method of claim 1, wherein the destination is the first location.
 12. The method of claim 1, wherein the notification is defined as sent from the first location.
 13. The method of claim 1, wherein the request to generate the first post data item is defined from a first application that is triggered to open by a second application.
 14. The method of claim 1, wherein the reference is a link is to the group of post data items at the first location when the group of post data items at the first location was interacted with by the user, and wherein the link is to the group of post data items at the second location when the group of post data items at the second location was interacted with by the user.
 15. The method of claim 1, wherein the reference is a link to the group of post data items at the most recent location between the first location and the second location that was interacted with by the user, the interaction by the user corresponding to the user providing a particular post data item of the group of post data items in reply to another post data item of the group of post data items at the first location or the second location. 